-
Notifications
You must be signed in to change notification settings - Fork 7.1k
removed adding the TaskPoolStrategy as it's not needed here #57897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request simplifies an example notebook by removing explicit compute strategy configuration (num_cpus, num_gpus, and compute=TaskPoolStrategy) from a ds.map() call. This change is well-justified as it removes an internal concept not suitable for an introductory example and makes the code consistent with other map calls in the notebook. The code now relies on Ray's sensible defaults, which improves simplicity and readability. The change is correct and I see no issues with it.
angelinalg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stamp
…ect#57897) Signed-off-by: xgui <[email protected]>
Signed-off-by: elliot-barn <[email protected]>
…ect#57897) Signed-off-by: Aydin Abiar <[email protected]>
…ect#57897) Signed-off-by: Future-Outlier <[email protected]>
Description
I have removed the line indicating the TaskPoolStrategy in the notebook. It's not needed here and it's an internal compute concept we shouldn't introduce for these introductory examples. Also, it is not used in the other ray data map calls in this example.